Add CI/CD pipeline that builds and deploys the app to the VM #12
+300
−17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
henrygr
force-pushed
the
deploy-script
branch
from
8355673 to
9485892
Compare
* Add a CI workflow that installs dependencies, checks formatting, lints, and typechecks; the Prisma client is generated first from a dummy env file since packages/db/src/generated is not committed * Replace the old template that ran `npm ci` and `npm run test`, which do not exist in this pnpm monorepo, so CI could never pass * Add a deploy workflow that runs when CI succeeds on main: it builds the frontend with the VM GraphQL URL baked in, syncs the repo to /srv/gspotter, installs dependencies, applies the Prisma schema, and installs and restarts systemd services for the backend (port 3001) and the SSR frontend (port 3000), then verifies both with curl * One-time VM prerequisites (node, pnpm, sudoers, Apache reverse proxy, PostgreSQL) are documented in the workflow file header
* Point the Apollo server at port 3001 so the API is reachable at [baseurl]:3001 * Set the Vite base path to /project2 so assets and routes resolve behind the Apache reverse proxy
* Add .output, dist, .nitro, .vinxi and .wrangler to the ESLint ignores so `pnpm lint` passes after a build
* Recent pnpm versions no longer read the "pnpm" field in package.json and fail the install with ERR_PNPM_IGNORED_BUILDS when a dependency's build scripts are unreviewed (strictDepBuilds) * Approve both packages in allowBuilds in pnpm-workspace.yaml, the new home of the setting, and in the legacy onlyBuiltDependencies list for older pnpm versions; both postinstall scripts are benign (a version-scheme check and the standard napi-postinstall binary preparation)
* apps/frontend gained react-leaflet and @types/leaflet without a matching lockfile update, which makes every `pnpm install --frozen-lockfile` fail
* #11 landed while CI was broken, so Map.tsx, __root.tsx and about.tsx were merged without passing `prettier --check`
henrygr
force-pushed
the
deploy-script
branch
from
9485892 to
e8af63a
Compare
nicolare
approved these changes
Oct 15, 2026
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this does
ci.yaml): install → prettier check → ESLint → typecheck. The committed template rannpm ci/npm run test, which don't exist in this pnpm monorepo, so CI could never pass — and the deploy workflow is chained on its success. The Prisma client is generated in CI from a dummy env file (packages/db/src/generatedis gitignored).deploy-to-vm.yaml), runs automatically when CI succeeds onmain:VITE_GRAPHQL_URLbaked in/srv/gspotteron the VM, installs dependencies, and applies the Prisma schema (db:push)gspotter-backend(GraphQL on port 3001) andgspotter-frontend(SSR on port 3000)/project2.output,dist,.nitro,.vinxi,.wrangler) sopnpm lintpasses after a buildOne-time VM setup (details in the deploy workflow header)
sudo npm i -g pnpm@10, installed system-wide so systemd can find themALL=(root) NOPASSWD: /usr/bin/install, /usr/bin/tee, /usr/bin/systemctlpnpm db:setup(see README)ProxyPass /project2 http://localhost:3000/project2(plus reverse), so the frontend is served at[baseurl]/project2— it is an SSR Node server, not static files